Join optimization in a database

ABSTRACT

A database server receives a query from a remote application server that is associated with a calculation scenario. The calculation scenario defines a data flow model that includes one or more calculation nodes that each define one or more operations to execute on the database server. The database server can be a column-oriented database and at least one of the calculation nodes comprises at least one join operation. Thereafter, the database server instantiates the calculation scenario so that it is optimized by removing one or more join operations and associated branches within the calculation scenario. The database server then executes the operations defined by the calculation nodes of the optimized calculation scenario to result in a responsive data set. The database server then provides the data set to the application server.

TECHNICAL FIELD

The subject matter described herein relates to optimizing joins in a database such as a column oriented databases.

BACKGROUND

Data flow between an application server and a database server is largely dependent on the scope and number of queries generated by the application server. Complex calculations can involve numerous queries of the database server which in turn can consume significant resources in connection with data transport as well as application server-side processing of transported data. Calculation engines can sometimes be employed by applications and/or domain specific languages in order to effect such calculations. Such calculation engines can execute calculation models/scenarios that comprise a plurality of hierarchical calculation nodes.

There are various applications in which tables with columns having one designation (e.g., technical names) can be enriched with more descriptive information from one or other tables. Such tables can be separate and joined using outer join operations when required. Some databases are unable to efficiently optimize such joins because the cardinality of the join is not known and the join cannot be completely removed if no columns are requested from an outer table. As a result, many of such outer joins are unnecessary which result in increased processing resource consumption (e.g., memory consumption, CPU consumption, etc.) and, in some cases, slower query response times.

SUMMARY

In one aspect, a database server receives a query from a remote application server that is associated with a calculation scenario. The calculation scenario defines a data flow model that includes one or more calculation nodes that each define one or more operations to execute on the database server. The database server can be a column-oriented database and at least one of the calculation nodes comprises at least one join operation. Thereafter, the database server instantiates the calculation scenario so that it is optimized by removing one or more join operations and associated branches within the calculation scenario. The database server then executes the operations defined by the calculation nodes of the optimized calculation scenario to result in a responsive data set. The database server then provides the data set to the application server.

At least one of the calculation nodes can include/specify at least one join operation specifies cardinality for the corresponding join operation. One or more of the join operations can be an outer join such as a left outer join or a right outer join.

At least a portion of paths and/or attributes defined by the calculation scenario can, in some implementations, not be required to respond to the query. In such cases, the instantiated calculation scenario can omit the paths and attributes defined by the calculation scenario that are not required to respond to the query.

At least one of the calculation nodes can filter results obtained from the database server. At least one of the calculation nodes can sort results obtained from the database server.

The calculation scenario can be instantiated in a calculation engine layer by a calculation engine. The calculation engine layer can interact with a physical table pool and a logical layer. The physical table pool can include physical tables containing data to be queried, and the logical layer can define a logical metamodel joining at least a portion of the physical tables in the physical table pool. The calculation engine can invoke an SQL processor for executing set operations.

An input for each calculation node can include one or more of: a physical index, a join index, an OLAP index, and another calculation node. Some or all calculation nodes can have at least one output table that is used to generate the data set. At least one calculation node can consume an output table of another calculation node.

The query can be forwarded to a calculation node in the calculation scenario that is identified as a default node if the query does not specify a calculation node at which the query should be executed. The calculation scenario can include database metadata.

Computer program products are also described that comprise non-transitory computer readable media storing instructions, which when executed one or more data processors of one or more computing systems, causes at least one data processor to perform operations herein. Similarly, computer systems are also described that may include one or more data processors and a memory coupled to the one or more data processors. The memory may temporarily or permanently store instructions that cause at least one processor to perform one or more of the operations described herein. In addition, methods can be implemented by one or more data processors either within a single computing system or distributed among two or more computing systems. Such computing systems can be connected and can exchange data and/or commands or other instructions or the like via one or more connections, including but not limited to a connection over a network (e.g. the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, or the like), via a direct connection between one or more of the multiple computing systems, etc.

The subject matter described herein provides many advantages. For example, context information about the structure of a table is used by a calculation engine to reduce query complexity which, in turn, increases query execution time while consuming fewer processing resources. In particular, with the current subject matter, a calculation engine optimizes outer join operations as a pre-cursor to conventional query-plan optimization.

The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a process flow diagram illustrating a method for optimizing join operations in a database;

FIG. 2 is a diagram illustrating a calculation engine layer, a logical layer, a physical table pool and their interrelationship;

FIG. 3 is a diagram illustrating an architecture for processing and execution control;

FIG. 4 is a diagram illustrating a stored calculation model for aggregation on top of a table;

FIG. 5 is a diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 4;

FIG. 6 is a diagram illustrating a stored calculation model for a join on top of tables;

FIG. 7 is a diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 6;

FIG. 8 is a first diagram illustrating a stored calculation model for an aggregation operation;

FIG. 9 is a first diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 8;

FIG. 10 is a second diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 8;

FIG. 11 is a first diagram illustrating a stored calculation model for a left outer join operation;

FIG. 12 is a first diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 11;

FIG. 13 is a second diagram illustrating a stored calculation model for a left outer join operation;

FIG. 14 is a first diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 13; and

FIG. 15 is a second diagram illustrating an executed calculation model corresponding to the stored calculation model of FIG. 13 with a different query as compared to the executed calculation model of FIG. 14.

DETAILED DESCRIPTION

FIG. 1 is a process flow diagram 100 illustrating a method in which, at 110, a query is received by a database server from a remote application server that is associated with a calculation scenario that defines a data flow model including one or more calculation nodes. Each calculation node defines one or more operations to execute on the database server. The database server can be a column-oriented database and at least one of the calculation nodes can include at least one join operation. Thereafter, at 120, the database server instantiates the optimized calculation scenario so that the calculation scenario is optimized by removing one or more join operations and associated branches within the calculation scenario. Subsequently, at 130, the operations defined by the calculation nodes of the instantiated calculation scenario can be executed to result in a responsive data set. Next, at 140, the data set is provided to the application server by the database server.

FIG. 2 is a diagram 200 that illustrates a database system in which there are three layers, a calculation engine layer 210, a logical layer 220, and a physical table-pool 230. Calculation scenarios can be executed by a calculation engine which can form part of a database or which can be part of the calculation engine layer 210 (which is associated with the database). The calculation engine layer 210 can be based on and/or interact with the other two layers, the logical layer 220 and the physical table pool 230. The basis of the physical table pool 230 consists of physical tables (called indexes) containing the data. Various tables can then be joined using logical metamodels defined by the logical layer 220 to form a new index. For example, the tables in a cube (OLAP view) can be assigned roles (e.g., fact or dimension tables) and joined to form a star schema. It is also possible to form join indexes, which can act like database view in environments such as the Fast Search Infrastructure (FSI) by SAP AG.

As stated above, calculation scenarios can include individual calculation nodes 211-214, which in turn each define operations such as joining various physical or logical indexes and other calculation nodes (e.g., CView 4 is a join of CView 2 and CView 3). That is, the input for a calculation node 211-214 can be one or more physical, join, or OLAP views or calculation nodes. A calculation node as used herein represents a operation such as a projection, aggregation, join, union, minus, intersection, and the like. Additionally, as described below, in addition to a specified operation, calculation nodes can sometimes be enhanced by filtering and/or sorting criteria. In some implementations, calculated attributes can also be added to calculation nodes.

In calculation scenarios, two different representations can be provided. First, a stored (“pure”) calculation scenario in which all possible attributes are given. Second, an instantiated/executed model that contains only the attributes requested in the query (and required for further calculations). Thus, calculation scenarios can be created that can be used for various queries. With such an arrangement, calculation scenarios can be created which can be reused by multiple queries even if such queries do not require every attribute specified by the calculation scenario. For on-the-fly scenarios this means that the same calculation scenario (e.g., in XML format, etc.) can be used for different queries and sent with the actual query. The benefit is that on application server side the XML description of a calculation scenario can be used for several queries and thus not for each possible query one XML has to be stored.

Further details regarding calculation engine architecture and calculation scenarios can be found in U.S. Pat. No. 8,195,643, the contents of which are hereby fully incorporated by reference.

FIG. 3 is a diagram 300 illustrating a sample architecture for request processing and execution control. As shown in FIG. 3, artifacts 305 in different domain specific languages can be translated by their specific compilers 310 into a common representation called a “calculation scenario” 315 (illustrated as a calculation model). To achieve enhanced performance, the models and programs written in these languages are executed inside the database server. This arrangement eliminates the need to transfer large amounts of data between the database server and the client application. Once the different artifacts 305 are compiled into this calculation scenario 315, they can be processed and executed in the same manner. The execution of the calculation scenarios 315 is the task of a calculation engine 320.

The calculation scenario 315 can be a directed acyclic graph with arrows representing data flows and nodes that represent operations. Each calculation node has a set of inputs and outputs and an operation that transforms the inputs into the outputs. In addition to their primary operation, each calculation node can also have a filter condition for filtering the result set. The inputs and the outputs of the operations can be table valued parameters (i.e., user-defined table types that are passed into a procedure or function and provide an efficient way to pass multiple rows of data to the application server). Inputs can be connected to tables or to the outputs of other calculation nodes. Calculation scenarios 315 can support a variety of node types such as (i) nodes for set operations such as projection, aggregation, join, union, minus, intersection, and (ii) SQL nodes that execute a SQL statement which is an attribute of the node. In addition, to enable parallel execution, a calculation scenario 315 can contain split and merge operations. A split operation can be used to partition input tables for subsequent processing steps based on partitioning criteria. Operations between the split and merge operation can then be executed in parallel for the different partitions. Parallel execution can also be performed without split and merge operation such that all nodes on one level can be executed in parallel until the next synchronization point. Split and merge allows for enhanced/automatically generated parallelization. If a user knows that the operations between the split and merge can work on portioned data without changing the result he or she can use a split. Then, the nodes can be automatically multiplied between split and merge and partition the data.

Calculation scenarios 315 are more powerful than traditional SQL queries or SQL views for many reasons. One reason is the possibility to define parameterized calculation schemas that are specialized when the actual query is issued. Unlike a SQL view, a calculation scenario 315 does not describe the actual query to be executed. Rather, it describes the structure of the calculation. Further information is supplied when the calculation scenario is executed. This further information can include parameters that represent values (for example in filter conditions). To obtain more flexibility, it is also possible to refine the operations when the model is invoked. For example, at definition time, the calculation scenario 315 may contain an aggregation node containing all attributes. Later, the attributes for grouping can be supplied with the query. This allows having a predefined generic aggregation, with the actual aggregation dimensions supplied at invocation time. The calculation engine 320 can use the actual parameters, attribute list, grouping attributes, and the like supplied with the invocation to instantiate a query specific calculation scenario 315. This instantiated calculation scenario 315 is optimized for the actual query and does not contain attributes, nodes or data flows that are not needed for the specific invocation.

When the calculation engine 320 gets a request to execute a calculation scenario 315, it can first optimize the calculation scenario 315 using a rule based model optimizer 322. Examples for optimizations performed by the model optimizer can include “pushing down” filters and projections so that intermediate results 326 are narrowed down earlier, or the combination of multiple aggregation and join operations into one node. The optimized model can then be executed by a calculation engine model executor 324 (a similar or the same model executor can be used by the database directly in some cases). This includes decisions about parallel execution of operations in the calculation scenario 315. The model executor 324 can invoke the required operators (using, for example, a calculation engine operators module 328) and manage intermediate results. Most of the operators are executed directly in the calculation engine 320 (e.g., creating the union of several intermediate results). The remaining nodes of the calculation scenario 315 (not implemented in the calculation engine 320) can be transformed by the model executor 324 into a set of logical database execution plans. Multiple set operation nodes can be combined into one logical database execution plan if possible.

The model optimizer 322 can be configured to enable dynamic partitioning based on one or more aspects of a query and/or datasets used by queries. The model optimizer can implement a series of rules that are triggered based on attributes of incoming datasets exceeding specified thresholds. Such rules can, for example, apply thresholds each with a corresponding a parallelization factor. For example, if the incoming dataset has 1 million rows then two partitions (e.g., parallel jobs, etc.) can be implemented, or if the incoming dataset has five million rows then five partitions (e.g., parallel jobs, etc.) can be implemented, and the like.

The attributes of the incoming datasets utilized by the rules of model optimizer 322 can additionally or alternatively be based on an estimated and/or actual amount of memory consumed by the dataset, a number of rows and/or columns in the dataset, and the number of cell values for the dataset, and the like.

The calculation engine 320 typically does not behave in a relational manner. The main reason for this is the instantiation process. The instantiation process can transform a stored calculation model 315 to an executed calculation model 315 based on a query on top of a calculation view which is a (catalog) column view referencing one specific node of a stored calculation model 315. Therefore, the instantiation process can combine the query and the stored calculation model and build the executed calculation model.

The main difference between a relational view or SQL with subselects and a calculation model is that the projection list in a relational view is stable also if another SQL statement is stacked on top whereas in a calculation model the projection list of each calculation node in the calculation model is depending on the projection list of the query or the parent calculation node(s).

With a calculation model 315, a user can provide a set of attributes/columns on each calculation node that can be used by the next calculation node or the query. If attributes/columns are projected in a query or on the parent calculation node, then just a subset of these requested attributes/columns can be considered in the executed calculation model.

The following examples (with reference to FIGS. 4-10) illustrate the difference between a stored calculation model and an executed calculation model:

FIG. 4 shows a stored calculation model 400 for an aggregation on top of a table that is a sums up K1 and K2 grouped by A, B, C. FIG. 5 shows an executed calculation model 500 and query that corresponds to the stored calculation model 400 of FIG. 4 in which in a first table calculation node only the attributes/columns A, K1 are in the projection list and in a second table calculation node, only the attributes/columns A, K1 are in the projection list.

FIG. 6 shows a stored calculation model 600 for a join on top of the illustrated tables. FIG. 7 shows an executed calculation model 700 and query that corresponds to the stored calculation model 600 of FIG. 6 in which the attribute A is added to the projection list at a join node and the underlying nodes (because such an arrangement is required for joins).

FIG. 8 shows a stored calculation model 800 for aggregation. With this stored calculation model 800, semantics can change depending on the attributes/columns requested by the calculation engine 320. Further, with the stored calculation model 800 of FIG. 8, the aggregation calculation node defines a calculated attribute. FIG. 9 shows a first executed calculation model 900 and query that corresponds to the stored calculation model 800 of FIG. 8 in which the aggregation over the table attribute A is added to a projection list due to the calculated attribute C_Attr. FIG. 10 shows a second executed calculation model 1000 and query that corresponds to the stored calculation model 800 of FIG. 8 and in which the Attribute A is not added to the projection list of the aggregation (because the calculated attribute C_Attr. was not queried).

The calculation engine 320 can extend joins in such a way that the application designer can set cardinality information in the calculation model 315 at every join operation. Such an arrangement is advantageous because application designers typically have a high level of knowledge about cardinalities which, in turn, can be used to set static filters in the calculation models 315 (which can ensure certain cardinalities). For example, filters can be applied on client and language fields which are widely used in tables.

Based on the cardinality information provided during design-time by the application designer, the calculation engine 320 can remove unnecessary join operations when the following conditions are met:

Depending on the join type, the cardinality and the requested attributes, the calculation engine 320 does not execute a join operation and removes branches required for the join operation for optimization.

-   -   LEFT (OUTER) JOIN, cardinality 1:1 or N:1, if no attribute from         the right table is requested or included in a where condition.     -   RIGHT (OUTER) JOIN, cardinality 1:1 or 1:N, if no attribute from         the left table is requested or included in a where condition.

While the example above is with regard to outer joins, the current subject matter can be also applied to inner joins. However, the problem on inner joins is that the impact on the result is high and when the application designer sets the wrong cardinality the results can be very different because in inner join can reduce the result table. This restriction (no optimization on inner joins) makes the feature more robust from an application designer perspective.

In addition to the removal of a join operation, the calculation engine 320 can also eliminate additional join-attributes that are required to perform the join. As stated above, the current subject matter can reduce a number of requested columns on source tables in calculation views generated by the calculation engine 320 for various queries. In order to implement the optimizations described herein, the calculation engine 320 should not request the join attributes on the predecessor node when the join is removed by the model optimizer 322 but rather a projection along attributes B, C was modeled for execution.

FIG. 11 shows a stored calculation model 1100 for a left outer join across two tables. FIG. 12 shows an executed calculation model 1200 with corresponding query that corresponds to the stored calculation model 1100 of FIG. 11 (after instantiation and optimization by the model optimizer 322). In this case, the left outer join was removed by the model optimizer 322 which provides the same results in a more efficient manner. FIG. 13 shows a stored calculation model 1300 for another left outer join. FIG. 14 is an executed calculation model 1400 with corresponding query that corresponds to the stored calculation model 1300 which was optimized using conventional techniques in which a projection is performed on top of an aggregation on top of a table. FIG. 15, in contrast, is an executed calculation model 1500 with query that corresponds to the stored calculation model 1300 of FIG. 13 (after optimization by the model optimizer 322). With this example, the instantiation process and the model optimizer 322 can remove the join node and reduce the aggregation node so that it does not implicate the previous needed join attribute A. Compared to the instantiated and optimized model 1400 from FIG. 14, the projection list (respective list of requested attributes) can be further optimized because, due to the cardinality information, the join attribute A can be optimized out. The explicitly provided cardinality information allows this optimization with the certainty that the result of the query will be correct. The designer of the calculation model needs the knowledge about the semantic of the base tables to be able to provide the cardinality information and to ensure that query results remain correct with this advanced join optimization.

One or more aspects or features of the subject matter described herein may be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device (e.g., mouse, touch screen, etc.), and at least one output device.

These computer programs, which can also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logical programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device, such as for example magnetic discs, optical disks, memory, and Programmable Logic Devices (PLDs), used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. The machine-readable medium can store such machine instructions non-transitorily, such as for example as would a non-transient solid state memory or a magnetic hard drive or any equivalent storage medium. The machine-readable medium can alternatively or additionally store such machine instructions in a transient manner, such as for example as would a processor cache or other random access memory associated with one or more physical processor cores.

To provide for interaction with a user, the subject matter described herein can be implemented on a computer having a display device, such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, such as for example visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including, but not limited to, acoustic, speech, or tactile input. Other possible input devices include, but are not limited to, touch screens or other touch-sensitive devices such as single or multi-point resistive or capacitive trackpads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like.

The subject matter described herein may be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user may interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

The subject matter described herein can be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. The implementations set forth in the foregoing description do not represent all implementations consistent with the subject matter described herein. Instead, they are merely some examples consistent with aspects related to the described subject matter. Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations can be provided in addition to those set forth herein. For example, the implementations described above can be directed to various combinations and subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. In addition, the logic flow(s) depicted in the accompanying figures and/or described herein do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Other implementations may be within the scope of the following claims. 

What is claimed is:
 1. A method comprising: receiving, by a database server from a remote application server, a query associated with a calculation scenario that defines a data flow model that includes one or more calculation nodes, each calculation node defining one or more operations to execute on the database server, the database server comprising a column-oriented database, at least one of the calculation nodes comprising at least one join operation and specifying cardinality for the at least one join operation, the cardinality for the at least one join operation specified at design time for the calculation scenario; instantiating, by the database server, the calculation scenario, the instantiating optimizing the calculation scenario by removing one or more join operations of the at least one join operation and associated branches within the calculation scenario, the removing based on the specified cardinality, a join type for the at least one join operation, and one or more attributes requested by the query; executing, by the database server, the operations defined by the calculation nodes of the optimized calculation scenario to result in a responsive data set having a result table with a row for each column in the column-oriented database implicated by the query having a constant value; and providing, by the database server to the application server, the data set.
 2. A method as in claim 1, wherein one or more of the join operations comprises a left outer join or a right outer join.
 3. A method as in claim 1, wherein at least a portion of paths and/or attributes defined by the calculation scenario are not required to respond to the query, and wherein the instantiated calculation scenario omits the paths and attributes defined by the calculation scenario that are not required to respond to the query.
 4. A method as in claim 1, wherein at least one of the calculation nodes filters results obtained from the database server.
 5. A method as in claim 1, wherein at least one of the calculation nodes sorts results obtained from the database server.
 6. A method as in claim 1, wherein the calculation scenario is instantiated in a calculation engine layer by a calculation engine.
 7. A method as in claim 6, wherein the calculation engine layer interacts with a physical table pool and a logical layer, the physical table pool comprising physical tables containing data to be queried, and the logical layer defining a logical metamodel joining at least a portion of the physical tables in the physical table pool.
 8. A method as in claim 6, wherein the calculation engine invokes an SQL processor for executing set operations.
 9. A method as in claim 1, wherein an input for each calculation node comprises one or more of: a physical index, a join index, an OLAP index, and another calculation node.
 10. A method as in claim 9, wherein each calculation node has at least one output table that is used to generate the data set.
 11. A method as in claim 10, wherein at least one calculation node consumes an output table of another calculation node.
 12. A method as in claim 1, wherein the executing comprises: forwarding the query to a calculation node in the calculation scenario that is identified as a default node if the query does not specify a calculation node at which the query should be executed.
 13. A method as in claim 1, wherein the calculation scenario comprises database metadata.
 14. A method as in claim 1, wherein the removing of the one or more join operations comprises not executing the at least one join operation.
 15. A system comprising: a database server comprising memory and at least one data processor; an application server in communication with and remote from the database server comprising memory and at least one data processor; wherein the database server: receives a query from the application server that is associated with a calculation scenario that defines a data flow model that includes one or more calculation nodes, each calculation node defining one or more operations to execute on the database server, the database server comprising a column-oriented database, at least one of the calculation nodes comprising at least one join operation and specifying cardinality for the at least one join operation, the cardinality for the at least one join operation specified at design time for the calculation scenario; instantiates the calculation scenario, the instantiating optimizing the calculation scenario by removing one or more join operations of the at least one join operation and associated branches within the calculation scenario, the removing based on the specified cardinality, a join type for the at least one join operation, and one or more attributes requested by the query; executes the operations defined by the calculation nodes of the optimized calculation scenario to result in a responsive data set having a result table with a row for each column in the column-oriented database implicated by the query having a constant value; and provides the data set to the application server.
 16. A system as in claim 15, wherein there are a plurality of application servers coupled to the database server.
 17. A system as in claim 15, wherein the database server executes three layers, a calculation engine layer, a logical layer, and a physical table pool.
 18. A system as in claim 15, wherein at least a portion of paths and/or attributes defined by the calculation scenario are not required to respond to the query, and wherein the instantiated calculation scenario omits the paths and attributes defined by the calculation scenario that are not required to respond to the query.
 19. A system as in claim 15, wherein the calculation scenario is instantiated in a calculation engine layer by a calculation engine, wherein the calculation engine layer interacts with a physical table pool and a logical layer, the physical table pool comprising physical tables containing data to be queried, and the logical layer defining a logical metamodel joining at least a portion of the physical tables in the physical table pool, wherein an input for each calculation node comprises one or more of: a physical index, a join index, an OLAP index, and another calculation node; wherein each calculation node has at least one output table that is used to generate the final result set.
 20. A non-transitory computer program product storing instructions, which when executed by at least one data processor of at least one computing system, result in operations comprising: receiving a query associated with a calculation scenario that defines a data flow model that includes one or more calculation nodes, each calculation node defining one or more operations to execute on the database server, the database server comprising a column-oriented database, at least one of the calculation nodes comprising at least one join operation and specifying cardinality for the at least one join operation, the cardinality for the at least one join operation specified at design time for the calculation scenario; instantiating the calculation scenario, the instantiating optimizing the calculation scenario by removing one or more join operations of the at least one join operation and associated branches within the calculation scenario, the removing based on the specified cardinality, a join type for the at least one join operation, and one or more attributes requested by the query; executing the operations defined by the calculation nodes of the optimized calculation scenario to result in a responsive data set having a result table with a row for each column in the column-oriented database implicated by the query having a constant value; and providing the data set. 